PACKAGE WL6b - LUNCH STATUS UI COMPATIBILITY FIX

Problem
- WL6 backend correctly enforced the lunch cap, but lunch-status.php returned new field names.
- The existing attendance app.js expects:
  has_open_session
  can_start
  can_end
  lunch_closed
- Because has_open_session was missing, the app thought the staff member was not clocked in for lunch use.
- Result: Start Working Lunch and End Working Lunch buttons stayed disabled even after clock-in.

Fix
- Replaces /api/lunch-status.php only.
- Adds backwards-compatible response fields required by existing app.js.
- Keeps WL6 lunch cap logic intact.

Extract inside
- /home/uent/public_html

Files
- /api/lunch-status.php
- /sql/verify-wl6b-lunch-status-ui-compatibility.sql
- /README-WL6b.txt

After extraction
1. Open attendance app.
2. Press Ctrl+F5 or hard refresh.
3. Log in.
4. If already clocked in, Start Working Lunch should be clickable.
5. If working lunch has started, End Working Lunch should be clickable.

Expected lunch-status responses
- Not clocked in:
  has_open_session = false
  can_start = false
  can_end = false

- Clocked in, lunch not started:
  has_open_session = true
  can_start = true
  can_end = false

- Working lunch open:
  has_open_session = true
  can_start = false
  can_end = true

- Working lunch closed:
  has_open_session = true
  can_start = false
  can_end = false
  lunch_closed = true
